<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Global Internet Business Solutions ~ GIBS</title> 
        <link>https://gibs.com</link> 
        <description>RSS feeds for Global Internet Business Solutions ~ GIBS</description> 
        <ttl>60</ttl> <item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/53/Logging_SSIS_information_to_the_Windows_Event_Log#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=53</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=53&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Logging SSIS information to the Windows Event Log</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/53/Logging_SSIS_information_to_the_Windows_Event_Log</link> 
    <description>First you need to add, using System.Diagnostics. &amp;nbsp;This provides the hook to the classes that will enable you to push your error to the Windows Event Log. &amp;nbsp;Now create the object to interact with it:
EventLog evLog = new EventLog(&quot;Application&quot;, System.Environment.MachineName, &quot;FlexMLS Image Import&quot;);

Read more: http://josef-richberg.squarespace.com/journal/2010/1/31/sending-ssis-information-to-the-windows-event-log.html#ixzz4cEmpUz5s</description> 
    <dc:creator></dc:creator> 
    <pubDate>Fri, 24 Mar 2017 10:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:53</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/69/DNN_Region_Lookup#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=69</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=69&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>DNN Region Lookup</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/69/DNN_Region_Lookup</link> 
    <description>&amp;nbsp;
 (SELECT [Value] FROM Lists where EntryID = (SELECT PropertyValue FROM UserProfile WHERE UserId = U.UserId AND PropertyDefinitionID = (SELECT PropertyDefinitionID FROM ProfilePropertyDefinition WHERE PropertyName = &#39;Region&#39; AND PortalID = @PortalID)))
 AS [State] </description> 
    <dc:creator></dc:creator> 
    <pubDate>Tue, 16 Feb 2016 11:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:69</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/77/SQL_Server_Reporting_Services_Permissions_Error#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=77</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=77&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>SQL Server Reporting Services Permissions Error</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/77/SQL_Server_Reporting_Services_Permissions_Error</link> 
    <description>To get this resolved you need to start you Internet Explorer as Administrator -&gt; Run as Administrator then open the url http://&lt;Server name&gt;/Reports this will take you to the "SQL Server Reporting Services" Home page

    Click on the "Folder Settings" button.
    Click on the "New Role Assignment" button.
    Add the Group or user name: DOMAIN\USER_NAME, and permissions you have logged in as.
    Click on Ok button.

This should resolve the issue.</description> 
    <dc:creator></dc:creator> 
    <pubDate>Wed, 24 Dec 2014 11:33:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:77</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/78/Pivot_Query_for_Ventrian_Property_Agent#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=78</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=78&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Pivot Query for Ventrian Property Agent</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/78/Pivot_Query_for_Ventrian_Property_Agent</link> 
    <description>I had a need for getting a property details for a SSR report and came up with the following store procedure&amp;nbsp; . . . I thought it might be useful to someone.
/****** Object: StoredProcedure [dbo].[GIBS_Rentals_Get_PropertyDetails] Script Date: 12/15/2014 06:52:03 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
&amp;nbsp;
CREATE PROCEDURE [dbo].[GIBS_Rentals_Get_PropertyDetails] 
( 
 @PropertyID int
)
AS
BEGIN
SET NOCOUNT ON;
DECLARE @cols AS VARCHAR(MAX),
 @query AS VARCHAR(MAX),
 @PropertyIDVarchar AS VARCHAR(10)
Set @PropertyIDVarchar = Convert(VARCHAR(10),@PropertyID)
select @cols = STUFF((SELECT distinct &#39;,&#39; + QUOTENAME(name) 
FROM Ventrian_PropertyAgent_CustomField 
FOR XML PATH(&#39;&#39;), TYPE
).value(&#39;.&#39;, &#39;VARCHAR(MAX)&#39;) 
,1,1,&#39;&#39;)
--print @cols
set @query 
= &#39;SELECT PropertyID,&#39; + @cols + &#39; from 
(
SELECT
PropertyID ,
&amp;nbsp;
cast(Ventrian_PropertyAgent_PropertyValue.CustomValue as Varchar(50)) AS CustomValue,
Ventrian_PropertyAgent_CustomField.Name AS [Name]
&amp;nbsp;
FROM Ventrian_PropertyAgent_PropertyValue
INNER JOIN
Ventrian_PropertyAgent_CustomField ON Ventrian_PropertyAgent_PropertyValue.CustomFieldID = Ventrian_PropertyAgent_CustomField.CustomFieldID
&amp;nbsp;
WHERE Ventrian_PropertyAgent_PropertyValue.PropertyID = &#39; + @PropertyIDVarchar + &#39;
) x
pivot
(
min(CustomValue)
 for Name in (&#39; + @cols + &#39;)
) p &#39;
--print @query
execute(@query)
END</description> 
    <dc:creator></dc:creator> 
    <pubDate>Mon, 15 Dec 2014 13:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:78</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/83/Get_a_List_of_all_Databases_on_a_SQL_Server_Installation#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=83</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=83&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Get a List of all Databases on a SQL Server Installation</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/83/Get_a_List_of_all_Databases_on_a_SQL_Server_Installation</link> 
    <description>Get a list of the database names and database size in a sql server instance using tsql:
EXEC sp_databases</description> 
    <dc:creator></dc:creator> 
    <pubDate>Fri, 24 Oct 2014 09:57:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:83</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/84/SQL_Timeout_on_Custom_DNN_module#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=84</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=84&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>SQL Timeout on Custom DNN module</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/84/SQL_Timeout_on_Custom_DNN_module</link> 
    <description>Try running . . . .
exec sp_updatestats;</description> 
    <dc:creator></dc:creator> 
    <pubDate>Wed, 08 Oct 2014 19:33:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:84</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/88/Replace_Null_or_Empty_Value_with_String#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=88</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=88&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Replace Null or Empty Value with String</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/88/Replace_Null_or_Empty_Value_with_String</link> 
    <description>Select ISNULL(NULLIF(GIBS_FBLineItems.ReportType, &#39;&#39;), &#39;--Undefined--&#39;) as ReportType from GIBS_FBLineItems</description> 
    <dc:creator></dc:creator> 
    <pubDate>Tue, 16 Sep 2014 10:28:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:88</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/116/Identify_SQL_User_Roles#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=116</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=116&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Identify SQL User Roles</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/116/Identify_SQL_User_Roles</link> 
    <description>select dp2.name as role, dp1.name as owner from sys.database_principals as dp1 inner join sys.database_principals as dp2 on dp1.principal_id = dp2.owning_principal_id where dp1.name = &#39;myUserName&#39;</description> 
    <dc:creator></dc:creator> 
    <pubDate>Thu, 18 Oct 2012 09:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:116</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/130/How_to_Shrink_Your_DotNetNuke_Database_Log_File__Truncate_Transaction_Log#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=130</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=130&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>How to Shrink Your DotNetNuke Database Log File / Truncate Transaction Log</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/130/How_to_Shrink_Your_DotNetNuke_Database_Log_File__Truncate_Transaction_Log</link> 
    <description>PROCEDURE: This article tells you how to shrink a DotNetNuke&amp;nbsp;database&amp;rsquo;s log file via Microsoft&amp;rsquo;s SQL Server Management Studio.
1) Log into your Management Studio.
2) Right click on the database
3) Select &amp;ldquo;Properties&amp;rdquo;
4) Click on &amp;ldquo;Options&amp;rdquo;
5) Change the recovery model to &amp;ldquo;Simple&amp;rdquo;
6) Click &amp;ldquo;OK&amp;rdquo;
7) Right click on the database
8) Select &amp;ldquo;Tasks&amp;rdquo; then &amp;ldquo;Shrink&amp;rdquo; and finally &amp;ldquo;Database&amp;rdquo;
9) Click &amp;ldquo;OK&amp;rdquo;
10) Right click on the database
11) Select &amp;ldquo;Properties&amp;rdquo;
12) Click on &amp;ldquo;Options&amp;rdquo;
13) Change the recovery model to &amp;ldquo;Full&amp;rdquo;
14) You can now restart your website.</description> 
    <dc:creator></dc:creator> 
    <pubDate>Sat, 31 Dec 2011 13:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:130</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/152/Finding_the_Port_of_MS_SQL_Named_Instance#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=152</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=152&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Finding the Port of MS SQL Named Instance</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/152/Finding_the_Port_of_MS_SQL_Named_Instance</link> 
    <description>When running a named instance of MS&amp;#160;SQL the instance will run on a port other than the usual port&amp;#160;1433. To determine the port you can use the following query:

DECLARE @tcp_port nvarchar(5)
EXEC xp_regread
@rootkey&amp;#160;&amp;#160;&amp;#160; =&amp;#160;&amp;#160;&amp;#160; &#39;HKEY_LOCAL_MACHINE&#39;,
@key&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; =&amp;#160;&amp;#160;&amp;#160; &#39;SOFTWARE\MICROSOFT\Microsoft SQL Server\MSSQL\MSSQLSERVER\SUPERSOCKETNETLIB\TCP&#39;,
@value_name&amp;#160;&amp;#160;&amp;#160; =&amp;#160;&amp;#160;&amp;#160; &#39;TcpPort&#39;,
@value&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160; =&amp;#160;&amp;#160;&amp;#160; @tcp_port OUTPUT
select @tcp_port

In my case the instance was named &quot;MSSQL&quot;.</description> 
    <dc:creator></dc:creator> 
    <pubDate>Thu, 17 Mar 2011 10:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:152</guid> 
    
</item>
<item>
    <comments>https://gibs.com/Support/Knowledge-Base/ID/167/Create_a_New_Database_From_an_Existing_Database_Backup_SQL_Server_Management_Studio#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://gibs.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=51&amp;ModuleID=411&amp;ArticleID=167</wfw:commentRss> 
    <trackback:ping>https://gibs.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=167&amp;PortalID=0&amp;TabID=51</trackback:ping> 
    <title>Create a New Database From an Existing Database Backup (SQL Server Management Studio)</title> 
    <link>https://gibs.com/Support/Knowledge-Base/ID/167/Create_a_New_Database_From_an_Existing_Database_Backup_SQL_Server_Management_Studio</link> 
    <description>
This topic explains how to create a new database from an existing full database backup.


    
        
            Security Note
        
        
            
            We recommend that you do not attach or restore databases from unknown or untrusted sources. Such databases could contain malicious code that might execute unintended Transact-SQL code or cause errors by modifying the schema or the physical database structure. Before you use a database from an unknown or untrusted source, run DBCC CHECKDB on the database on a nonproduction server and also examine the code, such as stored procedures or other user-defined code, in the database.
            
        
    




    
        
            Important
        
        
            
            Under the full or bulk-logged recovery model, before you can restore a database in SQL Server Management Studio, you must back up the active transaction log (known as the tail of the log). For more information, see How to: Back Up a Transaction Log (SQL Server Management Studio).
            
        
    



To create a new database from an existing full backup


    
    After you connect to the appropriate instance of the SQL Server Database Engine, in Object Explorer, click the server name to expand the server tree.
    
    
    Right-click Databases, point to Restore, and then click Database. Clicking Database opens the Restore Database dialog box.
    
    
    On the General page, the name of the source database appears in the To database list by default. To create the new database, enter its name in the list box.
    
    
    In the To a point in time text box, either use the default (Most recent possible) or click the browse button to select a specific date and time.
    
    
    To specify the source and location of the backup sets to restore, click one of the following options:
    
        
        From database
        Enter a database name in the list box.
        
        
        From device
        Click the browse button. This opens the Specify Backup dialog box. In the Backup media list, select one of the listed device types. To select one or more devices for the Backup location list, click Add.
        After you add the device or devices you want to the Backup location list, click OK to return to the General page.
        
    
    
    
    In the Select the backup sets to restore grid, select the backups to restore. This grid displays the backups available for the specified location. By default, a recovery plan is suggested. To override the suggested recovery plan, you can change the selections in the grid. Backups that depend on the restoration of an earlier backup are automatically deselected when the earlier backup is deselected.
    For information about the columns in the Select the backup sets to restore grid, see Restore Database (General Page).
    
    
    To view or select the advanced options, click Options in the Select a page pane.
    
    
    In the Restore options panel, optionally select any of the options:
    
        
        Overwrite the existing database
        
        
        Preserve the replication settings
        
        
        Prompt before restoring each backup
        
        
        Restrict access to the restored database
        
    
    For complete descriptions of theses options of the Restore options panel, see Restore Database (Options Page).
    
    
    You can move the database that you are restoring by specifying new restore destinations for the files in the Restore the database files as grid. The grid lists the original full path for each data or log file of the database and the restore destination for each file.
    The following table describes the columns of the Restore the database files as grid.
    &amp;#160;
    
    
        
            
                
                Header
                
                
                Values
                
            
            
                
                Original File Name
                
                
                The full path of a data file or log file of the original database.
                
            
            
                
                Restore As
                
                
                The path and file name that will be used as the restore destination for this data file or log file.
                To move the database that you are restoring to a different location, edit the Restore As field of each file and specify the new destination path or file name, or both.
                Also, if you want to restore a copy of a database on the server instance while the original database is still attached, you must specify a new database name in the To database field on the General page of the Restore Database dialog box.
                
                
                Note
                Changing the restore destinations in the Restore As column is equivalent to using the MOVE option in RESTORE statements.
                
                
                
            
        
    
    
    
    
    The Recovery state panel determines the state of the database after the restore operation. The default behavior is to:
    
        
        Leave the database ready for use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored. (RESTORE WITH RECOVERY)
        
        
            
                
                    Note
                
                
                    
                    Choose this option only if you are restoring all the necessary backups now.
                    
                
            
        
        
        
    
    Alternatively, you can select to either:
    
        
        Leave the database non-operational, and do not roll back the uncommitted transactions. Additional transaction logs can be restored. (RESTORE WITH NORECOVERY)
        
        
        Leave the database in read-only mode. Undo uncommitted transactions, but save the undo actions in a standby file so that recovery effects can be reverted. (RESTORE WITH STANDBY)
        
    
    For descriptions of the options of the Restore options panel, see Restore Database (Options Page).
    


&amp;#160;</description> 
    <dc:creator></dc:creator> 
    <pubDate>Mon, 20 Dec 2010 12:52:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:167</guid> 
    
</item>

    </channel>
</rss>